-
Notifications
You must be signed in to change notification settings - Fork 19
feat: update stagedUpdateRun to use latest resource snapshot #320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat: update stagedUpdateRun to use latest resource snapshot #320
Conversation
…ex is unset Signed-off-by: Britania Rodriguez Reyes <britaniar@microsoft.com>
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
|
We also need to account for resourceSnapshotIndex access here https://github.com/britaniar/kubefleet/blob/bff950842f01cab0eb0041401ed4ef7134581848/pkg/controllers/updaterun/execution.go#L99. I think it's better to populate the ResourceSnapshotIndex field in the spec by a defaulter instead from the latest resource snapshot. Ideally once set ResourceSnapshotIndex should not change in the middle of an updateRun. Edit: after offline discussion it's better to store resourceSnapshotName as a field on the updateRun status instead we don't want to change spec since it's an user facing object |
Signed-off-by: Britania Rodriguez Reyes <britaniar@microsoft.com>
e34c1db to
1c44de9
Compare
Description of your changes
Fixes #
I have:
Updated API to make ResourceSnapshotIndex optional. in staged update run
Update the initialization stage of staged update run to check if ResourceSnapshotIndex is defined to find that specific resource snapshot. Otherwise, if not defined it will use the latest resource snapshot.
Added an integration test case where relevant.
Run
make reviewableto ensure this PR is ready for review.How has this code been tested
Special notes for your reviewer